Skip to main content

Home/ Open Web/ Group items tagged web OS

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Google Chrome OS: Web Platform To Rule Them All -- InformationWeek - 0 views

www.informationweek.com/...showArticle.jhtml

chromeOS OpenWeb Google HTML W3C

shared by Gary Edwards on 15 Jul 09 - Cached
  • Gary Edwards on 15 Jul 09
     
    Some good commentary on chrome OS from InformationWeek's Thomas Claburn. Excerpt: With Chrome OS, Google aims to make the Web the primary platform for software development....... The fact that Chrome OS applications will be written using open Web standards like JavaScript, HTML, and CSS might seem like a liability because Web applications still aren't as capable as applications written for specific devices and operating systems. But Google is betting that will change and is working to effect the change on which its bet depends. Within a year or two, Web browsers will gain access to peripherals, through an infrastructure layer above the level of device drivers. Google's work with standards bodies is making that happen..... ..... According to Matt Womer, the "ubiquitous Web activity lead" for W3C, the Web standards consortium, Web protocol groups are working to codify ways to access peripherals like digital cameras, the messaging stack, calendar data, and contact data. There's now a JavaScript API that Web developers can use to get GPS information from mobile phones using the phone's browser, he points out. What that means is that device drivers for Chrome OS will emerge as HTML 5 and related standards mature. Without these, consumers would never use Chrome OS because devices like digital cameras wouldn't be able to transfer data. Womer said the standardization work could move quite quickly, but won't be done until there's an actual implementation. That would be Chrome OS...... ..... Chrome OS will sell itself to developers because, as Google puts it, writing applications for the Web gives "developers the largest user base of any platform."
Gary Edwards

New Adobe Air 2.0 Released : ISEdb.COM - 0 views

www.isedb.com/...Page1.html

Adobe-Air WebKit Silverlight AJAX

shared by Gary Edwards on 19 Nov 09 - Cached
  • Gary Edwards on 19 Nov 09
     
    Is Adobe AiR a Virtual Desktop?  We expect a VD to run an alien OS and those OS specific applications.  With AiR 2.0 it seems Adobe has ditched the "OS" component of a VD, and the OS specific applications, but is quite capable of running AiR based applications and information services that would otherwise have been designed for a specific OS environment.   Another way of looking at this would be to say that VD's are designed to run existing OS and OS specific applications, while AiR is desinged to run newly written OS independent applications that have one very important advantage over legacy applications and information systems;  AiR speaks the language of the Web 3.0.   This is WebKit HTML5-CSS3 with an advanced but Air specific version of JavaScript called "ActionScript".  What Adobe doesn't do is provide support for other critically important aspects of the WebKit interactive Web 3.0 model: support for Canvas/SVG!  Adobe continues to push the proprietary SWF interactive vector graphics format.   Note that Microsoft's Silverlight universal runtime does not support anything in the WebKit Web 3.0 model!  It's all proprietary. excerpt: For the first time since 2007, Adobe has updated its Air platform, released recently in beta with a slew of new features. The features include support for detection of mass storage devices, advanced networking capabilities, ability to open a file with its default application, improved cross-platform printing, and a bunch of other things that you probably won't really notice in any other way other than your Adobe working significantly more efficiently and smoothly than before. The 2.0 version of Air also will be able to support HTML5 and CSS3, due to an upgrade of its WebKit. Developers will also be happy to know that they can create Air applications that can be installed through a native installer. Air's changes have seen it morph into something of an 'operating system sitting on an operating system'. According
Gary Edwards

XML Production Workflows? Start with the Web and XHTML - 1 views

quod.lib.umich.edu/...n-workflows-start-with-the-web

OpenWeb XML XHTML-CSS HTML5-CSS3-JavaScript IDML

shared by Gary Edwards on 01 Nov 13 - No Cached
  • Challenges: Some Ugly Truths The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition. Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper. A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition. And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5] But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
  • Practical Challenges In 2009, there is still no truly likeable—let alone standard—editing and authoring software for XML. For many (myself included), the high-water mark here was Adobe’s FrameMaker, substantially developed by the late 1990s. With no substantial market for it, it is relegated today mostly to the tech writing industry, unavailable for the Mac, and just far enough afield from the kinds of tools we use today that its adoption represents a significant hurdle. And FrameMaker was the best of the breed; most of the other software in decent circulation are programmers’ tools—the sort of things that, as Michael Tamblyn pointed out, encourage editors to drink at their desks. The labour question represents a stumbling block as well. The skill-sets and mind-sets that effective XML editors need have limited overlap with those needed by literary and more traditional production editors. The need to think of documents as machine-readable databases is not something that comes naturally to folks steeped in literary culture. In combination with the sheer time and effort that rich tagging requires, many publishers simply outsource the tagging to India, drawing a division of labour that spans oceans, to put it mildly. Once you have XML content, then what do you do with it? How do you produce books from it? Presumably, you need to be able to produce print output as well as digital formats. But while the latter are new enough to be generally XML-friendly (e-book formats being largely XML based, for instance), there aren’t any straightforward, standard ways of moving XML content into the kind of print production environments we are used to seeing. This isn’t to say that there aren’t ways of getting print—even very high-quality print—output from XML, just that most of them involve replacing your prepress staff with Java programmers.
  • Why does this have to be so hard? It’s not that XML is new, or immature, or untested. Remember that the basics have been around, and in production, since the early 1980s at least. But we have to take account of a substantial and long-running cultural disconnect between traditional editorial and production processes (the ones most of us know intimately) and the ways computing people have approached things. Interestingly, this cultural divide looked rather different in the 1970s, when publishers were looking at how to move to digital typesetting. Back then, printers and software developers could speak the same language. But that was before the ascendancy of the Desktop Publishing paradigm, which computerized the publishing industry while at the same time isolating it culturally. Those of us who learned how to do things the Quark way or the Adobe way had little in common with people who programmed databases or document-management systems. Desktop publishing technology isolated us in a smooth, self-contained universe of toolbars, grid lines, and laser proofs. So, now that the reasons to get with this program, XML, loom large, how can we bridge this long-standing divide?
  • ...44 more annotations...
  • Using the Web as a Production Platform The answer, I think, is right in front of you. The bridge is the Web, a technology and platform that is fundamentally based on XML, and which many publishers are by now comfortably familiar with. Perhaps not entirely comfortably, but at least most publishers are already working with the Web; they already either know or have on staff people who understand it and can work with it. The foundation of our argument is this: rather than looking at jumping to XML in its full, industrial complexity, which seems to be what the O'Reilly-backed StartWithXML initiative[6] is suggesting, publishers instead leverage existing tools and technologies—starting with the Web—as a means of getting XML workflows in place. This means making small investments and working with known tools rather than spending tens of thousands of dollars on XML software and rarefied consultants. It means re-thinking how the existing pieces of the production toolchain fit together; re-thinking the existing roles of software components already in use. It means, fundamentally, taking the Web seriously as a content platform, rather than thinking of it as something you need to get content out to, somehow. If nothing else, the Web represents an opportunity to think about editorial and production from outside the shrink-wrapped Desktop Publishing paradigm.
  • Is the Web made of Real XML? At this point some predictable objections can be heard: wait a moment, the Web isn’t really made out of XML; the HTML that makes up most of the Web is at best the bastard child of SGML, and it is far too flaky/unstructured/underpowered to be taken seriously. We counter by arguing that although HTML on the Web exists in a staggering array of different incarnations, and that the majority of it is indeed an unstructured mess, this does not undermine the general principle that basic, ubiquitous Web technologies can make a solid platform for content management, editorial process, and production workflow.
  • With the advent of a published XML standard in the late 1990s came the W3C’s adoption of XHTML: the realization of the Web’s native content markup as a proper XML document type. Today, its acceptance is almost ubiquitous, even while the majority of actual content out there may not be strictly conforming. The more important point is that most contemporary Web software, from browsers to authoring tools to content management systems (from blogs to enterprise systems), are capable of working with clean, valid XHTML. Or, to put the argument the other way around, clean, valid XHTML content plays absolutely seamlessly with everything else on the Web.[7]
  • The objection which follows, then, will be that even if we grant that XHTML is a real XML document type, that it is underpowered for “serious” content because it is almost entirely presentation (formatting) oriented; it lacks any semantic depth. In XHTML, a paragraph is a paragraph is a paragraph, as opposed to a section or an epigraph or a summary.
  • n contrast, more “serious” XML document types like DocBook[8] or DITA-derived schemas[9] are capable of making semantic distinctions about content chunks at a fine level of granularity and with a high degree of specificity.
  • So there is an argument for recalling the 80:20 rule here. If XHTML can provide 80% of the value with just 20% of the investment, then what exactly is the business case for spending the other 80% to achieve that last 20% of value? We suspect the ratio is actually quite a bit steeper than 80:20 for most publishers.
  • Furthermore, just to get technical for a moment, XHTML is extensible in a fairly straightforward way, through the common “class” attribute on each element. Web developers have long leveraged this kind of extensibility in the elaboration of “microformats” for semantic-web applications.[10] There is no reason why publishers shouldn’t think to use XHTML’s simple extensibility in a similar way for their own ends.
  • XHTML, on the other hand, is supported by a vast array of quotidian software, starting with the ubiquitous Web browser. For this very reason, XHTML is in fact employed as a component part of several more specialized document types (ONIX and ePub among them).
  • Why re-invent a general-purpose prose representation when XHTML already does the job?
  • It is worth pausing for a moment to consider the role of XHTML in the ePub standard for ebook content. An ePub file is, anatomically, a simply disguised zip archive. Inside the zip archive are a few standard component parts: there are specialized files that declare metadata about the book, and about the format of the book. And then there is the book’s content, represented in XHTML. An ePub book is a Web page in a wrapper.
  • To sum up the general argument: the Web as it already exists presents incredible value to publishers, as a platform for doing XML content management with existing (and often free) tools, and without having to go blindly into the unknown. At this point, we can offer a few design guidelines: prefer existing and/or ubiquitous tools over specialized ones wherever possible; prefer free software over proprietary systems where possible; prefer simple tools controlled and coordinated by human beings over fully automated (and therefore complex) systems; play to our strengths: use Web software for storing and managing content, use layout software for layout, and keep editors and production people in charge of their own domains.
  • Putting the Pieces Together: A Prototype
  • At the SFU Master of Publishing Program, we have been chipping away at this general line of thinking for a few years. Over that time, Web content management systems have been getting more and more sophisticated, all the while getting more streamlined and easier to use. (NB: if you have a blog, you have a Web content management system.) The Web is beginning to be recognized as a writing and editing environment used by millions of people. And the ways in which content is represented, stored, and exchanged online have become increasingly robust and standardized.
  • The missing piece of the puzzle has been print production: how can we move content from its malleable, fluid form on line into the kind of high-quality print production environments we’ve come to expect after two decades of Desktop Publishing?
  • Anyone who has tried to print Web content knows that the existing methods leave much to be desired (hyphenation and justification, for starters). In the absence of decent tools for this, most publishers quite naturally think of producing the print content first, and then think about how to get material onto the Web for various purposes. So we tend to export from Word, or from Adobe, as something of an afterthought.
  • While this sort of works, it isn’t elegant, and it completely ignores the considerable advantages of Web-based content management.
  • Content managed online is stored in one central location, accessible simultaneously to everyone in your firm, available anywhere you have an Internet connection, and usually exists in a much more fluid format than Word files. If only we could manage the editorial flow online, and then go to print formats at the end, instead of the other way around. At SFU, we made several attempts to make this work by way of the supposed “XML import” capabilities of various Desktop Publishing tools, without much success.[12]
  • In the winter of 2009, Adobe solved this part of the problem for us with the introduction of its Creative Suite 4. What CS4 offers is the option of a complete XML representation of an InDesign document: what Adobe calls IDML (InDesign Markup Language).
  • The IDML file format is—like ePub—a simply disguised zip archive that, when unpacked, reveals a cluster of XML files that represent all the different facets of an InDesign document: layout spreads, master pages, defined styles, colours, and of course, the content.
  • IDML is a well thought-out XML standard that achieves two very different goals simultaneously: it preserves all of the information that InDesign needs to do what it does; and it is broken up in a way that makes it possible for mere mortals (or at least our Master of Publishing students) to work with it.
  • What this represented to us in concrete terms was the ability to take Web-based content and move it into InDesign in a straightforward way, thus bridging Web and print production environments using existing tools and skillsets, with a little added help from free software.
  • We would take clean XHTML content, transform it to IDML-marked content, and merge that with nicely designed templates in InDesign.
  • The result is an almost push-button publication workflow, which results in a nice, familiar InDesign document that fits straight into the way publishers actually do production.
  • Tracing the steps To begin with, we worked backwards, moving the book content back to clean XHTML.
  • The simplest method for this conversion—and if you want to create Web content, this is an excellent route—was to use Adobe’s “Export to Digital Editions” option, which creates an ePub file.
  • Recall that ePub is just XHTML in a wrapper, so within the ePub file was a relatively clean XHTML document. It was somewhat cleaner (that is, the XHTML tagging was simpler and less cluttered) than InDesign’s other Web-oriented exports, possibly because Digital Editions is a well understood target, compared with somebody’s website.
  • In order to achieve our target of clean XHTML, we needed to do some editing; the XHTML produced by InDesign’s “Digital Editions” export was presentation-oriented. For instance, bulleted list items were tagged as paragraphs, with a class attribute identifying them as list items. Using the search-and-replace function, we converted such structures to proper XHTML list and list-item elements. Our guiding principle was to make the XHTML as straightforward as possible, not dependent on any particular software to interpret it.
  • We broke the book’s content into individual chapter files; each chapter could then carry its own basic metadata, and the pages conveniently fit our Web content management system (which is actually just a wiki). We assembled a dynamically generated table of contents for the 12 chapters, and created a cover page. Essentially, the book was entirely Web-based at this point.
  • When the book chapters are viewed online, they are formatted via a CSS2 stylesheet that defines a main column for content as well as dedicating screen real estate for navigational elements. We then created a second template to render the content for exporting; this was essentially a bare-bones version of the book with no navigation and minimal styling. Pages (or even the entire book) can be exported (via the “Save As...” function in a Web browser) for use in either print production or ebook conversion. At this point, we required no skills beyond those of any decent Web designer.
  • Integrating with CS4 for Print Adobe’s IDML language defines elements specific to InDesign; there is nothing in the language that looks remotely like XHTML. So a mechanical transformation step is needed to convert the XHTML content into something InDesign can use. This is not as hard as it might seem.
  • Both XHTML and IDML are composed of straightforward, well-documented structures, and so transformation from one to the other is, as they say, “trivial.” We chose to use XSLT (Extensible Stylesheet Language Transforms) to do the work. XSLT is part of the overall XML specification, and thus is very well supported in a wide variety of tools. Our prototype used a scripting engine called xsltproc, a nearly ubiquitous piece of software that we found already installed as part of Mac OS X (contemporary Linux distributions also have this as a standard tool), though any XSLT processor would work.
  • In other words, we don’t need to buy InCopy, because we just replaced it with the Web. Our wiki is now plugged directly into our InDesign layout. It even automatically updates the InDesign document when the content changes. Credit is due at this point to Adobe: this integration is possible because of the open file format in the Creative Suite 4.
  • We wrote an XSLT transformation script[18] that converted the XHTML content from the Web into an InCopy ICML file. The script itself is less than 500 lines long, and was written and debugged over a period of about a week by amateurs (again, the people named at the start of this article). The script runs in a couple of seconds, and the resulting .icml file can then be “placed” directly into an InDesign template. The ICML file references an InDesign stylesheet, so the template file can be set up with a house-styled layout, master pages, and stylesheet definitions for paragraphs and character ranges.
  • Rather than a public-facing website, our system relies on the Web as a content management platform—of course a public face could easily be added.
  • It should be noted that the Book Publishing 1 proof-of-concept was artificially complex; we began with a book laid out in InDesign and ended up with a look-alike book laid out in InDesign. But next time—for instance, when we publish Book Publishing 2—we can begin the process with the content on the Web, and keep it there throughout the editorial process. The book’s content could potentially be written and edited entirely online, as Web content, and then automatically poured into an InDesign template at proof time. “Just in time,” as they say. This represents an entirely new way of thinking of book production. With a Web-first orientation, it makes little sense to think of the book as “in print” or “out of print”—the book is simply available, in the first place online; in the second place in derivative digital formats; and third, but really not much more difficult, in print-ready format, via the usual InDesign CS print production system publishers are already familiar with.
  • Creating Ebook Files Creating electronic versions from XHTML source is vastly simpler than trying to generate these out of the existing print process. The ePub version is extremely easy to generate; so is online marketing copy or excerpts for the Web, since the content begins life Web-native.
  • Since an ePub file is essentially XHTML content in a special wrapper, all that is required is that we properly “wrap” our XHTML content. Ideally, the content in an ePub file is broken into chapters (as ours was) and a table of contents file is generated in order to allow easy navigation within an ebook reader. We used Julian Smart’s free tool eCub[19] to simply and automatically generate the ePub wrapper and the table of contents. The only custom development we did was to create a CSS stylesheet for the ebook so that headings and paragraph indents looked the way we wanted. Starting with XHTML content, creating ePub is almost too easy.
  • today, we are able to put the process together using nothing but standard, relatively ubiquitous Web tools: the Web itself as an editing and content management environment, standard Web scripting tools for the conversion process, and the well-documented IDML file format to integrate the layout tool.
  • Our project demonstrates that Web technologies are indeed good enough to use in an XML-oriented workflow; more specialized and expensive options are not necessarily required. For massive-scale enterprise publishing, this approach may not offer enough flexibility, and the challenge of adding and extracting extra semantic richness may prove more trouble than it's worth.
  • But for smaller firms who are looking at the straightforward benefits of XML-based processes—single source publishing, online content and workflow management, open and accessible archive formats, greater online discoverability—here is a way forward.
  • The result is very simple and easy to use. Our demonstration requires that a production editor run the XSLT transformation script manually, but there is no reason why this couldn’t be built directly into the Web content management system so that exporting the content to print ran the transformation automatically. The resulting file would then be “placed” in InDesign and proofed.
  • The final piece of our puzzle, the ability to integrate print production, was made possible by Adobe's release of InDesign with an open XML file format. Since the Web's XHTML is also XML, is can be easily and confidently transformed to the InDesign format.
  • Such a workflow—beginning with the Web and exporting to print—is surely more in line with the way we will do business in the 21st century, where the Web is the default platform for reaching audiences, developing content, and putting the pieces together. It is time, we suggest, for publishers to re-orient their operations and start with the Web.
  • Using the Web as a Production Platform
  • Gary Edwards on 01 Nov 13
     
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. As an after thought, i was thinking that an alternative title to this article might have been, "Working with Web as the Center of Everything".
Gary Edwards

Google Drops A Nuclear Bomb On Microsoft. And It's Made of Chrome. - 0 views

www.techcrunch.com/...crosoft-and-its-made-of-chrome

chrome google windows

shared by Gary Edwards on 08 Jul 09 - Cached
  • Gary Edwards on 08 Jul 09
     
    Introducing the Chrome OS alternative to Windows: excerpt: What Google is doing is not recreating a new kind of OS, they're creating the best way to not need one at all. So why release this new OS instead of using Android? After all, it has already been successfully ported to netbooks. Google admits that there is some overlap there. But a key difference they don't mention is the ability to run on the x86 architecture. Android cannot do that (though there are ports), Chrome OS can and will. But more, Google wants to emphasize that Chrome OS is all about the web, whereas Android is about a lot of different things. Including apps that are not standard browser-based web apps. But Chrome OS will be all about the web apps. And no doubt HTML 5 is going to be a huge part of all of this. A lot of people are still wary about running web apps for when their computer isn't connected to the web. But HTML 5 has the potential to change that, as you'll be able to work in the browser even when not connected, and upload when you are again.
Gary Edwards

In Mobile, Fragmentation is Forever. Deal With It. - washingtonpost.com - 0 views

www.washingtonpost.com/...AR2010030402374.html

webkit-html5 OpenWeb-Standards Web-apps OpenWeb-Productivity-Platform

shared by Gary Edwards on 04 Mar 10 - Cached
  • Gary Edwards on 04 Mar 10
     
    I disagree with the authors conclusions here.  He misses some very significant developments.  Particularly around Google, WebKit, and WebKit-HTML5. For instance, there is this article out today; "Google Really is Giving Away Free Nexus One and Droid Handsets to Developers".  Also, Palm is working on a WiMAX/WiFi version of their WebOS (WebKit) smartphone for Sprint.  Sprint and ClearWire are pushing forward with a very aggressive WiMAX rollout in the USA.  San Francisco should go on line this year!   One of the more interesting things about the Sprint WiMAX plan is that they have a set fee of $69.00 per month that covers EVERYTHING; cellphone, WiMAX Web browsing, video, and data connectivity, texting (SMS) and VOIP.  Major Sprint competitors, Verizon, AT&T and TMobile charge $69 per month, but it only covers cellphone access.  Everything else is extra adn also at low speed/ low bandwidth.  3G at best.  WiMAX however is a 4G screamer.  It's also an open standard.  (Verizon FIOS and LTE are comparable and said to be coming soon, but they are proprietary technologies).   The Cable guys are itneresting in that they are major backers of WiMAX, but also have a bandwidth explosive technology called Docsis. There is an interesting article at TechCrunch, "In Mobile, Fragmentation is Forever. Deal With It."  I disagree entirely with the authors conclusion.  WebKit is capable of providing a universal HTML5 application developers layer for mobile and desktop browser computing.  It's supported by Apple, Google, Palm (WebOS), Nokia, RiMM (Blackberry) and others to such an extent that 85% of all smartphones shipped this year will either ship with WebKit or, an Opera browser compatible with the WebKit HTML5 document layout/rendering model.   I would even go as far as to say that WebKit-HTML5 owns the Web's document model and application layer for the future.  Excepting for Silverlight, which features the OOXML document model with over 500 million desktop develop
Paul Merrell

Mozilla partners with Panasonic to bring Firefox OS to the TV, details progress on tabl... - 0 views

thenextweb.com/...s-work-tablet-desktop-versions

Firefox-OS

shared by Paul Merrell on 07 Jan 14 - No Cached
  • At CES 2014 in Las Vegas today, Mozilla announced its plans for Firefox OS this year. Having launched Firefox OS for smartphones in 2013, the company has now partnered with Panasonic to bring its operating system to TVs, and also detailed the progress that has been made around the tablet and desktop versions.
  • Mereby elaborated that current options are controlled by either Google or Apple, two major corporations that “hold all the strings.” As such, Android and iOS are not viable options for Panasonic, as the ecosystem is tightly controlled. With Firefox OS, however, Mereby argues that “anyone can compete”, as you can operate your own marketplace. Not only can Panasonic open up its own marketplace for apps and content, but those who want to build apps and sell content can bypass marketplaces and make their offerings directly to Firefox OS users.
  • While the partnership is not exclusive, Panasonic will be the first to release next-generation smart TVs powered by Firefox OS. Mozilla and Panasonic will work together to promote Firefox OS and its open ecosystem on the big screen. The plan is to leverage existing HTML5 and Web technologies used on PCs, smartphones, and tablets, to provide TVs with more personalized and optimized access to content and services through the Internet. Mozilla’s Web APIs for hardware control and operation will allow TVs to monitor and operate devices, such as emerging smart home appliances, inside and outside of the home. Basic functions such as menus and programming guides, which are currently written as embedded programs, will be written in HTML5, letting developers easily create applications for smartphones or tablets to remotely access and operate TVs. Mozilla also envisions personalized user interfaces with users’ favorites and new functions for multiple users sharing the same screen.
  • ...1 more annotation...
  • Last but not least, Mozilla wanted to underline how Firefox OS was coming to the desktop. Since the operating system is open source, anyone can modify it. VIA is doing just that: it’s making its own changes to create a more suitable version for the desktop, and Mozilla is bringing those commits back to its own repository. Furthermore, VIA today announced the availability of APC Paper and Rock, two new devices that offer a preview of Firefox OS running in a desktop environment. Rock is a motherboard which can be inserted into any barebone PC chassis while Paper is a standalone computer with its own case. Both are targeted at early adopters and developers wanting to help find, file, and fix bugs for VIA’s desktop version of Firefox OS. Paper and Rock are available with the same buildable source codes currently available on GitHub.
Gary Edwards

Google talks Chrome OS, HTML5, and the future of software - 1 views

arstechnica.com/...chrome-os-interview-1.ars

chrome-OS HTML5 Google

shared by Gary Edwards on 22 Jan 10 - Cached
  • Gary Edwards on 22 Jan 10
     
    Matthew Papakipos, the engineering director for the Chrome OS project, and Eitan Bencuya, from Google PR. Over the course of the interview, Papakipos and Bencuya go into considerable detail about topics that range from big-picture perspectives on how Google develops software and where it sees the Web going with HTML5, to the nuts and bolts of what Chrome OS is slated to offer in specific areas. In short, we cover the following ground: ... How and when the Chrome OS project was conceived... The relationship between Chrome OS and Android... How Google is trying to tackle the same "file handler" problem as Windows OLE and the registry, but in the cloud.... Who Google sees as the target audience for Chrome OS, how did they decide which projects and features to pursue... The convergence of the phone and the computer... Nuts and bolts details, like native client execution, security, and UI issues... The significance of Chrome's built-in media player
Gary Edwards

Windows 8: Microsoft's browser-based OS | ExtremeTech - 1 views

www.extremetech.com/...s-8-the-first-browser-based-os

Windows-8 Win8 HTML+ Native-HTML-Apps Open-Web-Productivity

shared by Gary Edwards on 13 Sep 11 - No Cached
  • Microsoft’s browser-based operating systemGet this: The entire Metro interface — the complete Windows 8 front-end — is powered by Internet Explorer 10. Not the browser with a back button and an address bar, but the IE10 rendering engine Trident. To drive this point home, Metro-style apps in Windows 8 can be written in HTML, CSS, and JavaScript, and they will be just as “low-level” as their C++ and C# cousins. In other words, Windows 8 runs web apps natively.
  • To put this into contrast, think about the current state-of-the-art in Chrome, Firefox, and Internet Explorer 9. Chrome has glorified extensions and bookmarks, Firefox is working on an Open Web App Store, and IE9 has pinned sites. Windows 8 will have web apps that are first-class citizens, capable of using all of the same hardware resources as any other compiled program — and it will all be powered by Internet Explorer 10.
  • It’s the great Web App Dream: write once, run anywhere.
  • ...7 more annotations...
  • All three versions are fundamentally identical.
  • What if Windows 8 is actually a success on the tablet? If Windows 8 becomes ubiquitous, so does Internet Explorer 10 — and if IE10 can be found on hundreds of millions of devices, what platform do you think developers will choose?
  • This poses a tricky question, though. You see, not only does IE10 power Windows 8′s primary interface, but Internet Explorer 10 — the browser — is also available as a Metro-style app, and as a full-interface browser in the Explorer Desktop.
  • Do you write an app for tens of millions of iPhones and iPads, or do you write a single piece of HTML, CSS, and JavaScript that can run perfectly on every Windows 8, IE10-powered tablet, laptop, and desktop?
  • Those same web apps, with a little tweaking, will probably even work with Chrome and Firefox and Safari — but here’s an uncomfortable truth: if Windows 8 reaches 90% penetration of the computing market, why bother targeting a web browser at all? Just write a native, Metro-style web app instead.
  • Finally, add in the fact that IE10 will almost certainly come to Windows Phone 8 next year, and you will have a single app container — AppX — that runs across every damn computer form factor.
  • Microsoft, threatened by the idea of OS-agnostic web apps and browser-based operating systems from Google and Mozilla, has just taken the game to a whole new level — and, rather shockingly, given that Windows 8 started its development in mid-2009, it would seem that the lumbering behemoth might have actually out-maneuvered Google
  • Gary Edwards on 13 Sep 11
     
    Excellent review of Windows 8, including some prescient thinking about what it means to have HTML+ Web Apps running natively on the Win8 OS platform.  The author/reviewer Sebastion Anthony suggest why this breakthrough is a problem for Google, Apple and Mozilla.  I'm wondering though; is this a problem for the Open Web future?  Or is this a positive step towards an Open Web communications and collaborative computation platform that  is used by all and owned by none?   After nearly thirty years of a love-hate-hate more than ever relationship with Microsoft, for sure Win8 and native HTML+ is something to carefully watch.
Gary Edwards

CPU Wars - Intel to Play Fab for an ARM Chipmaker: Understanding What the Altera Deal M... - 0 views

www.dailytech.com/...article33659.htm

OpenWeb WinTel Intel-ARM x86-ARM CPU-GPU

shared by Gary Edwards on 04 Nov 13 - No Cached
  • Intel wants x86 to conquer all computing spaces -- including mobile -- and is trying to leverage its process lead to make that happen.  However, it's been slowed by a lack of inclusion of 4G cellular modems on-die and difficulties adapting to the mobile market's low component prices.  ARM, meanwhile, wants a piece of the PC and server markets, but has received a lukewarm response from consumers due to software compatibility concerns. The disappointing sales of (x86) tablet products using Microsoft Corp.'s (MSFT) Windows 8 and the flop of Windows RT (ARM) product in general somewhat unexpectedly had the net result of being a driver to maintain the status quo, allowing neither company to gain much ground.  For Intel, its partnership with Microsoft (the historic "Wintel" combo) has damaged its mobile efforts, as Windows 8 flopped in the tablet market.  Likewise ARM's efforts to score PC market share were stifled by the flop of Windows RT, which led to OEMs killing off ARM-based laptops and convertibles.
  • Both companies seem to have learned their lesson and are migrating away from Windows towards other platforms -- in ARM's case Chromebooks, and in Intel's case Android tablets/smartphones. But suffice it to say, ARM Holdings and Intel are still very much bitter enemies from a sales perspective.
  • III. Profit vs. Risk -- Understanding the Modern CPU Food Chain
  • ...16 more annotations...
  • Whether it's tablets or PCs, the processor is still one of the most expensive components onboard.  Aside from the discrete GPU -- if a device has one -- the CPU has the greatest earning potential for a large company like Intel because the CPU is the most complex component. Other components like the power supply or memory tend to either be lower margin or have more competitors.  The display, memory, and storage components are all sensitive to process, but see profit split between different parties (e.g. the company who makes the DRAM chips and the company who sells the stick of DRAM) and are primarily dependent on process technology. CPUs and GPUs remain the toughest product to make, as it's not enough to simply have the best process, you must also have the best architecture and the best optimization of that architecture for the space you're competing in. There's essentially five points of potential profit on the processor food chain: [CPU] Fabrication [CPU] Architecture design [CPU] Optimization OEM OS platform Of these, the fabrication/OS point is the most profitable (but is dependent on the number of OEM adopters).  The second most profitable niche is optimization (which again is dependent on OEM adopter market share), followed by OEM markups.  In terms of expense, fabrication and operating system designs requires the greatest capital investment and the highest risk.
  • In terms of difficulty/risk, the fabrication and operating system are the most difficult/risky points.  Hence in terms of combined risk, cost, and profitability the ranking of which points are "best" is arguably: Optimization Architecture design OS platfrom OEM Fabrication ...with the fabrication point being last largely because it's so high risk. In other words, the last thing Intel wants is to settle into a niche of playing fabs for everybody else's product, as that's an unsound approach.  If you can't keep up in terms of chip design, you typically spin off your fabs and opt for a different architecture direction -- just look at Advanced Micro Devices, Inc.'s (AMD) spinoff of GlobalFoundries and upcoming ARM product to see that.
  • IV. Top Firms' Role on That Food Chain
  • Apple has seen unbelievable profits due to this fundamental premise.  It controls the two most desirable points on the food chain -- OS and optimization -- while sharing some profit with its architecture designer (ARM Holdings) and a bit with the fabricator (Samsung Electronics Comp., Ltd. (KSC:005930)).  By choosing to play operating system maker, too, it adds to its profits, but also its risk.  Note that nearly every other first-party exclusive smartphone platform has failed or is about to fail (i.e. BlackBerry, Ltd. (TSE:BB) and the now-dead Palm).
  • Intel controls points 1, 2, and 5, currently, on the food chain.  Compared to Apple, Intel's points of control offer less risk, but also slightly less profitability. Its architecture control may be at risk, but even so, it's currently the top in its most risky/expensive point of control (fabrication), where as Apple's most risky/expensive point of control (OS development) is much less of a clear leader (as Android has surpassed Apple in market share).  Hence Apple might be a better short-term investment, but Intel certainly appears a better long-term investment.
  • Samsung is another top company in terms of market dominance and profit.  It occupies points 1, 3, 4, and 5 -- sometimes.  Sometimes Samsung's devices use third-party optimization firms like Qualcomm Inc. (QCOM) and NVIDIA Corp. (NVDA), which hurts profitability by removing one of the most profitable roles.  But Samsung makes up for this by being one of the largest and most successful third party manufacturers.
  • Microsoft enjoys a lot of profit due to its OS dominance, as does Google Inc. (GOOG); but both companies are limited in controlling only one point which they monetize in different ways (Microsoft by direct sales; Google by giving away OS product for free in return for web services market share and by proxy search advertising revenue).
  • Qualcomm and NVIDIA are also quite profitable operating solely as optimizers, as is ARM Holdings who serves as architecture maker to Qualcomm, NVIDIA, Apple, and Samsung.
  • V. Four Scenarios in the x86 vs. ARM Competition
  • Scenario one is that x86 proves dominant in the mobile space, assuming a comparable process.
  • A second scenario is that x86 and ARM are roughly tied, assuming a comparable process.
  • A third scenario is that x86 is inferior to ARM at a comparable process, but comparable or superior to ARM when the x86 chip is built using a superior process.  From the benchmarks I've seen to date, I personally believe this is most likely.
  • A fourth scenario is that x86 is so drastically inferior to ARM architecturally that a process lead by Intel can't make up for it.
  • This is perhaps the most interesting scenario, in the sense of thinking of how Intel would react, if not overly likely.  If Intel were faced with this scenario, I believe Intel would simply bite the bullet and start making ARM chips, leveraging its process lead to become the dominant ARM chipmaker.  To make up for the revenue it lost, paying licensing fees to ARM Holdings, it could focus its efforts in the OS space (it's Tizen Linux OS project with Samsung hints at that).  Or it could look to make up for lost revenue by expanding its production of other basic process-sensitive components (e.g. DRAM).  I think this would be Intel's best and most likely option in this scenario.
  • VI. Why Intel is Unlikely to Play Fab For ARM Chipmakers (Even if ARM is Better)
  • From Intel's point of view, there is an entrenched, but declining market for x86 chips because of Windows, and Intel will continue to support Atom chips (which will be required to run Windows 8 tablets), but growth on desktops will come from 64 bit desktop/server class non-Windows ARM devices - Chromebooks, Android laptops, possibly Apple's desktop products as well given they are going 64 bit ARM for their future iPhones. Even Windows has been trying to transition (unsuccessfully) to ARM. Again, the Windows server market is tied to x86, but Linux and FreeBSD servers will run on ARM as well, and ARM will take a chunk out of the server market when a decent 64bit ARM server chip is available as a result.
  • Gary Edwards on 04 Nov 13
     
    Excellent article explaining the CPU war for the future of computing, as Intel and ARM square off.  Intel's x86 architecture dominates the era of client/server computing, with their famed WinTel alliance monopolizing desktop, notebook and server implementations.  But Microsoft was a no show with the merging mobile computing market, and now ARM is in position transition from their mobile dominance to challenge the desktop -notebook - server markets.   WinTel lost their shot at the mobile computing market, and now their legacy platforms are in play.  Good article!!! Well worth the read time  ................
Gary Edwards

Adeptol Viewing Technology Features - 0 views

www.ajaxdocumentviewer.com/features.asp

sursen florian wiki-word visual-document file-viewer

shared by Gary Edwards on 27 Jan 11 - No Cached
  • Gary Edwards on 27 Jan 11
     
    Quick LinksGet a TrialEnterprise On DemandEnterprise On PremiseFAQHelpContact UsWhy Adeptol?Document SupportSupport for more than 300 document types out of boxNot a Virtual PrinterMultitenant platform for high end document viewingNo SoftwaresNo need to install any additional softwares on serverNo ActiveX/PluginsNo plugins or active x or applets need to be downloaded on client side.Fully customizableAdvanced API offers full customization and UI changes.Any OS/Any Prog LanguageInstall Adeptol Server on any OS and integrate with any programming language.AwardsAdeptol products receive industry awards and accolades year after year  View a DemoAttend a WebcastContact AdeptolView a Success StoryNo ActiveX, No Plug-in, No Software's to download. Any OS, Any Browser, Any Programming Language. That is the Power of Adeptol. Adeptol can help you retain your customers and streamline your content integration efforts. Leverage Web 2.0 technologies to get a completely scalable content viewer that easily handles any type of content in virtually unlimited volume, with additional capabilities to support high-volume transaction and archive environments. Our enterprise-class infrastructure was built to meet the needs of the world's most demanding global enterprises. Based on AJAX technology you can easily integrate the viewer into your application with complete ease. Support for all Server PlatformsCan be installed on Windows   (32bit/64bit) Server and Linux   (32bit/64bit) Server. Click here to see technical specifications.Integrate with any programming languageWhether you work in .net, c#, php, cold fusion or JSP. Adeptol Viewer can be integrated easily in any programming language using the easy API set. It also comes with sample code for all languages to get you started.Compatibility with more than 99% of the browsersTested & verified for compatibility with 99% of the various browsers on different platforms. Click here to see browser compatibility report.More than 300 Document T
Gary Edwards

Mobile Enterprise: Android OS, Best Practices for Developing Mobile Strategies - 0 views

www.cmswire.com/...g-mobile-strategies-009837.php

sursen AppsGeyser Titanium

shared by Gary Edwards on 18 Jan 11 - No Cached
  • Gary Edwards on 18 Jan 11
     
    Convert Content for Android OS Making your content mobile friendly is harder than it sounds. However, more tools are emerging to help companies create content for multiple platforms, from iPads to smartphones, across a variety of operating systems. Recently, AppsGeyser privately launched a web platform that allows you to convert any web content to an Android App. With AppsGeyser companies can create an Android app three ways: Grabbing any website content block or web widget Copying and pasting HTML code, JavaScript, AJAX or Flash Entering the URL of your website Nifty tool for instantly converting web site widgets into Android Apps.  Looks like a new category of tools to make legacy Web services mobile-ready.  Titanium
Gary Edwards

Jolicloud Enables Google Docs Editing in File Manager - 0 views

www.cmswire.com/...ing-in-file-manager-010688.php

sync-share-store-collaboration JoliCloud Google-Chrome-OS

shared by Gary Edwards on 30 Mar 11 - No Cached
  • Gary Edwards on 30 Mar 11
     
    Very cool stuff.  Keep in mind that JoliCloud is Linux, based on Google Chrome OS.  I wonder how much of this is built into Chrome OS, or was done by JoliCloud? Jolicloud (news, site) has recently launched version 1.2, introducing several features and renaming the locally-installed cloud operating system into Joli OS. Among its latest additions was Dropbox integration into the file manager. In an update, Jolicloud has also announced better Google Docs integration for easier management, previewing and editing of online documents.
Gary Edwards

Meet Google, Your Phone Company - 0 views

gigaom.com/...meet-google-your-phone-company

wave unified-productivity google android chrome chromeOS webkit

shared by Gary Edwards on 15 Jul 09 - Cached
  • Gary Edwards on 15 Jul 09
     
    Om Malik has an interesting commentary on Google Voice, the Android OS, and a new gVoice application for iPhones and Androids. For sure, new gVoice app meshes into the Andorid OS as if it were hard coded into the silicon. I left a lengthy comment in the discussion section describing my experiences with gVoice and what i see emerging as Google's Unified Productivity Platform. Of course, gWave, Chrome, Chrome OS, webkit-HTML+, and the sweep of Google Web applications and service come into play. Excerpt: Can Google be your phone company? The answer is yes. I came to that conclusion after I met with Vincent Paquet, co-founder of GrandCentral (a company acquired by Google) and now a member of the Google Voice team. Earlier today he stopped by our office to show the mobile app versions of its Google Voice service for Blackberry and Android. Google recently announced that it was going to make the Voice service widely available to users in the U.S. soon.
Paul Merrell

Mozilla Developers Testing Mobile OS - HotHardware - 0 views

hothardware.com/...a-Developers-Testing-Mobile-OS

Mozilla web OS B2G boot to Gecko

shared by Paul Merrell on 08 Nov 11 - No Cached
  • Mozilla has been experimenting with an interesting idea called Boot 2 Gecko. Essentially, B2G (as it’s called) is a mobile operating system based on the Web, as opposed to what the project’s wiki calls “proprietary, single-vendor stacks”. Mozilla has something there--open Web technologies indeed increasingly provide an intriguing platform for lots of things, mobile and otherwise. The developers on the B2G project are looking at the following areas: New web APIs: build prototype APIs for exposing device and OS capabilities to content (Telephony, SMS, Camera, USB, Bluetooth, NFC, etc.) Privilege model: making sure that these new capabilities are safely exposed to pages and applications Booting: prototype a low-level substrate for an Android-compatible device Applications: choose and port or build apps to prove out and prioritize the power of the system
Gary Edwards

Google's Real Chrome OS Problem: Who's Going To Buy It? | SiliconValley Insider - 0 views

www.businessinsider.com/oblem-wheres-the-market-2009-7

ge chromeOS google google-wave

shared by Gary Edwards on 12 Jul 09 - Cached
  • Gary Edwards on 12 Jul 09
     
    .... "While i don't see Google or anyone else replacing the MSOffice productivity environment anytime soon, i do see Google challenging Microsoft wherever the Web comes into play. As for the future, that battle for desktop productivity will take place, just not with ChromeOS, Linux, or, the MacOS. What has to happen before the assault on the Microsoft's productivity empire can begin is that the business systems bound to the MSOffice productivity environment must transition to the Open Web, via SaaS or some other replacement. Or, the productivity environment itself must be re-purposed to the Open Web. The tricky part will be that re-purposing play. ChromeOS is a blockbuster announcement. Not a declaration of war, but a shot across the bow that shouts; Google will defend the Open Web, and profitable business they have there. ..... ~ge~
Gary Edwards

Adobe's Web Typography design work lands in WebKit browser | Deep Tech - CNET News - 0 views

news.cnet.com/...n-work-lands-in-webkit-browser

Adobe-CSS3 Web-Typography WebKit

shared by Gary Edwards on 06 Jun 11 - No Cached
  • Gary Edwards on 06 Jun 11
     
    Adobe has contributed the first "CSS Regions" patch to the OS WebKit project.  CSS Regions is at the core of Adobe's flowing Web Typography work, and has been submitted to the W3C CSS standardization effort.   No mention yet as to what kind of CSS3-HTML5 authoring and publication tools Adobe has in the works, but the inclusion in WebKit will no doubt shake things up in the world of visually-immersive packaging (FlipBoard, OnSwipe, TreeSaver, Needle, etc.) excerpt:Today, the first bit of Adobe-written code landed in the WebKit browser engine project, an early step to try to bring magazine-style layouts to Web pages using an extension to today's CSS (Cascading Style Sheets) technology. Adobe calls the technology CSS Regions. The move begins fulfilling a plan Adobe announced in May to build the technology into WebKit and--if the company can persuade others to embrace it--furthers Adobe's ambition to standardize the advanced CSS layout mechanism. WebKit
Gary Edwards

AppleInsider | Inside Mac OS X Snow Leopard: Exchange Support - 0 views

www.appleinsider.com/..._leopard_exchange_support.html

exchange apple iphone monopoly

shared by Gary Edwards on 06 Sep 09 - Cached
  • Gary Edwards on 06 Sep 09
     
    Apple desktop and iPhone support of Microsoft Exchange is not support for Microsoft, as some think.  It's actually a strategy to erode Microsoft's desktop monopoly.  It's also part of a longer term plan to thwart Microsoft's hopes of leveraging their desktop monopoly into a Web Server monopoly. Excerpt: Apple is reducing its dependance upon Microsoft's client software, weakening Microsoft's ability to hold back and dumb down its Mac offerings at Apple's expense. More importantly, Apple is providing its users with additional options that benefit both Mac users and the open source community. In the software business, Microsoft has long known the importance of owning the client end. It worked hard to displace Netscape's web browser in the late 90s, not because there was any money to be made in giving away browser clients, but because it knew that whoever controlled the client could set up proprietary demands for a specific web server. That's what Netscape had worked to do as it gave away its web browser in hopes that it could make money selling Netscape web servers; Microsoft first took control of the client with Internet Explorer and then began tying its IE client to its own IIS on the server side with features that gave companies reasons to buy all of their server software from Microsoft. As Apple takes over the client end of Exchange, it similarly gains market leverage. First and foremost, the move allows Apple to improve the Exchange experience of Mac users so that business users have no reason not to buy Macs. Secondly, it gives Apple a client audience to market its own server solutions, including MobileMe to individual users and Snow Leopard Server to organizations. In concert with providing Exchange Server support, Apple is also delivering integrated support for its own Exchange alternatives in both MobileMe and with Snow Leopard Server's improved Dovecot email services, Address Book Server, iCal Server, the new Mobile Access secure gateway, and its include
Gary Edwards

Apple, Microsoft Challenged By Streaming Software Plan - Cloud - 0 views

www.informationweek.com/...240154215

ORBX.JS JavaScript Javascript-library Native-Code

shared by Gary Edwards on 06 May 13 - No Cached
  • Gary Edwards on 06 May 13
     
    Very interesting the way JavaScript Libraries are continuing to challenge Native Code for Web Application dominance.    excerpt: "The code library, ORBX.js, can be thought of as a cloud-based alternative to Google's Native Client technology. It permits Linux, OS X and Windows applications to run on remote servers and to be presented in a Web browser." "With ORBX.js, native code and legacy applications can be hosted in the cloud (e.g. Amazon EC2), and stream interactive graphics, 3D rendering or low latency video to a standard HTML5 page without using plugins or native code, or even the video tag (which, like Google NaCL,is vendor specific - ORBX.js works on all five major browsers)," explained Otoy founder and CEO Jules Urbach in an email. "The video codec created for ORBX.js can decode 1080p60 at a quality on par with H.264, using only JavaScript." "With ORBX.js and a cloud service provider, you could conceivably run Value's PC Steam client on an Apple iMac or Google Chromebook. You could run Autodesk 3DS Max 2014 on an Android Nexus 7 tablet. You could run a big budget, graphically demanding game title like Left 4 Dead 2 in a Web browser, without any plugins, Flash, Java, NaCL or other supporting technology."
Gary Edwards

Adobe to Jobs: 'What the Flash do you know?' * The Register - 0 views

www.theregister.co.uk/...adobe_responds_to_apple

Apple Steve-Jobs WebKit Google Adobe-Flash HTML5

shared by Gary Edwards on 05 Feb 10 - Cached
  • Gary Edwards on 05 Feb 10
     
    Good quotes.  The Wired article is also worth reading.  The important take away being that Apple is fully committed to native browser HTML5.  So is Google.  But, i found out at the Web 2.0 - WebKit party in 2009, there is quite a bit of tension between Apple WebKit and Google.  The problem being that Apple is doing all the work while Google is pumping up HTML5, Web Sockets and Native Client; all of which are essential to WebKit, but also to Chrome OS, Chrome, Android and the Google Apps push. excerpt:  According to Wired, at an Apple "town hall" meeting after the introduction of the Flashless iPad, Steve Jobs unloaded on Google, calling the search giant's "don't be evil" motto "bullshit," before rounding on Adobe. "They are lazy. They have all this potential to do interesting things, but they just refuse to do it," he said. "Apple does not support Flash because it is so buggy... Whenever a Mac crashes more often than not it's because of Flash. No one will be using Flash...The world is moving to HTML5."
Gary Edwards

Flow - Chromium OS builds by Hexxeh - 1 views

chromeos.hexxeh.net

chrome-OS flow hexxeh ChromiumOS Chromium

shared by Gary Edwards on 22 Apr 10 - Cached
  • Gary Edwards on 22 Apr 10
     
    Flow is the latest in the line of Hexxeh's hugely popular ChromiumOS builds. Flow is the most exciting version yet, bringing even more hardware support, an auto-updater, webcam support and an improved application menu & directory. All this, requires only a 2GB USB drive (download size is 327MB) ChromiumOS is a lightweight, lightning-fast operating system for your netbook, laptop or even desktop. With the familiar environment of Chromium/Chrome, the entire web is at your fingertips in seconds. HTML5 & Flash are fully supported, allowing you to enjoy the very best that the web has to offer.
1 - 20 of 28 Next ›
Showing 20▼ items per page